Object lifecycle analysis tool

ABSTRACT

Embodiments presented herein provide techniques for generating analytical graphs that display a visualization of multiple transaction objects processed concurrently in a computer system. An object lifecycle analysis tool identifies one or more transaction objects having a specified identifier. Each transaction object corresponds to an instance of a common transaction having been processed. The analysis tool retrieves transition state information corresponding to each transaction object and sorts the transition state information in chronological order. The analysis tool generates a graph based on the sorted transition state information. The generated graph allows a user to easily identify performance issues (e.g., concurrency bottlenecks) in a transaction management system.

BACKGROUND

Many enterprises engage in commercial transactions. For instance, the financial industry frequently processes a high volume of payment transactions through multiple servers. Financial institutions, such as banks, handle numerous amounts of deposits, withdrawals, transfers, and the like on a daily basis. Because many of these transactions are time-sensitive, the transactions need to be processed efficiently.

To handle a high volume of transactions efficiently, servers process the transactions concurrently. Such processing may be executed using resources of each server. However, bottlenecks or non-concurrent pinch points may occur at different processing states for each transaction. These bottlenecks and pinch points hinder the ability of the servers to efficiently process the transactions.

Identifying where concurrency bottlenecks occur during processing may aid in preventing them from happening. One approach to do so is to examine and debug application code used to process the transactions. However, this approach presents several concerns. For example, the application code might be unavailable to an individual desiring to identify the bottlenecks. Further, even if the code is available, the individual might not have a thorough understanding of the application code.

SUMMARY

Embodiments presently disclosed herein provide a computer-implemented method. The method generally includes identifying one or more transaction objects having a specified identifier. Each of transaction objects corresponds to an instance of a common transaction having been processed. The method also includes retrieving transition state information corresponding to each transaction object. The method also includes sorting the transition state information for transaction object in chronological order. The method also includes generating a graph based on the sorted transition state information. The method generally includes identifying one or more transaction objects having a specified identifier. Each of transaction objects corresponds to an instance of a common transaction having been processed. The method also includes retrieving transition state information corresponding to each transaction object. The method also includes sorting the transition state information for transaction object in chronological order. The method also includes generating a graph based on the sorted transition state information.

Another embodiment of the invention includes a computer program product, the computer program product comprising a non-transitory computer-readable storage medium having computer-readable program code embodied therewith. The code, when executed on a processor, may generally be configured to perform an operation. The operation generally includes identifying one or more transaction objects having a specified identifier. Each of transaction objects corresponds to an instance of a common transaction having been processed. The operation also includes retrieving transition state information corresponding to each transaction object. The operation also includes sorting the transition state information for transaction object in chronological order. The operation also includes generating a graph based on the sorted transition state information. The operation generally includes identifying one or more transaction objects having a specified identifier. Each of transaction objects corresponds to an instance of a common transaction having been processed. The operation also includes retrieving transition state information corresponding to each transaction object. The operation also includes sorting the transition state information for transaction object in chronological order. The operation also includes generating a graph based on the sorted transition state information.

Still another embodiment of the invention includes a system having a processor and a memory containing an operation. The operation generally includes identifying one or more transaction objects having a specified identifier. Each of transaction objects corresponds to an instance of a common transaction having been processed. The operation also includes retrieving transition state information corresponding to each transaction object. The operation also includes sorting the transition state information for transaction object in chronological order. The operation also includes generating a graph based on the sorted transition state information. The operation generally includes identifying one or more transaction objects having a specified identifier. Each of transaction objects corresponds to an instance of a common transaction having been processed. The operation also includes retrieving transition state information corresponding to each transaction object. The operation also includes sorting the transition state information for transaction object in chronological order. The operation also includes generating a graph based on the sorted transition state information.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates an example computing environment, according to one embodiment.

FIG. 2 illustrates an example transaction state graph, according to one embodiment.

FIG. 3 illustrates an example transaction state graph, according to one embodiment.

FIG. 4 illustrates an object lifecycle analysis tool, according to one embodiment.

FIG. 5 illustrates a method diagram for generating a visualization of transition states of multiple objects, according to one embodiment.

FIG. 6 illustrates a computer system configured with an application tool configured to generate a visualization of transition states of multiple objects, according to one embodiment.

DETAILED DESCRIPTION

Embodiments presented herein provide techniques for generating a visualization of multiple transactions being processed concurrently in a system. The generated visualization may be used to analyze system performance of multithreaded processes throughout the system. For example, the visualization may be used to identify concurrency bottlenecks that occur while processing of the transactions.

In one embodiment, an analysis tool generates the visualizations. Applications that process transactions concurrently often store transition state information related to each individual transaction in transaction databases. In one embodiment, the analysis tool may be included with the transaction processing applications to use transaction data stored in such databases to generate the visualizations. The analysis tool retrieves information relevant to generating a visualization from transaction data stored in a transaction database. For example, such information may include transition state histories of each processed transaction. The transition state histories may include beginning and ending times of a particular transition state and a type of the transition state. The analysis tool organizes the data in chronological order. Once organized, the analysis tool generates a visual representation of lifecycles for each transaction based on the results from an initiation state to a completed state of a transaction.

The generated visualizations allow a system administrator (or other individual, such as a developer) to observe the efficiency and concurrency of a processing flow of multiple transactions. Through the graph, the individual may identify pinch points and bottlenecks in the overall transaction flow of the transaction. Such information allows the system administrator or developer to tune the transaction processing application to eliminate or reduce bottlenecks. Further, the system administrator may identify other performance issues, such as reduced throughput. Advantageously, graphs are generated using stored transaction data, analyses can be made without having to inspect application source code.

Note, the following description relies on a financial transaction management application as a reference example of an application having an analysis tool used to generate visualizations of object transition states. However, one of skill in the art will recognize that embodiments may be adapted for use in a variety of transaction-based contexts. For example, embodiments may be used by e-commerce-based services that process transactions concurrently and store transaction state data in a database. Generally, these techniques may be expanded to cover other transaction management systems and database sources.

FIG. 1 illustrates an example computing environment 100, according to one embodiment. As shown, the computing environment 100 includes multiple client devices 105 and an application server 120, each connected to a communications network 110. The application server 120 provides a multithreaded processing architecture for a financial transaction management application 125 that allows financial entities to integrate and optimize transactions with other financial entities. The financial transaction management application 125 processes, in parallel, a high volume of transaction objects. A transaction object is a set of operations that perform a task together. Examples of transaction objects in this context may be a deposit into an account, a transfer from one account to another, a payment transaction, etc., sent by the client devices 105. Note, although FIG. 1 depicts a single application server, multiple application servers may be deployed in the computing environment 100 to process the transactions sent by the client devices 105.

When the financial transaction management application 125 processes a transaction object, the transaction object enters various transition states. For instance, assume that a client device 105 initiates a payment transaction with the application server 120. An initial transition state of the payment transaction may be a “PAY_ORIG” state. An intermediary transition state may include a “GATEWAY_ACK” state. Another transition state may include a “PAYMENT_ACK” state. The transaction management application 125 may store the transition state data of each transaction object in a transaction database 130. In addition, the transaction management application 125 stores other information relevant to associating specific activity with a transaction object in the transaction database 130. For example, the transaction management application 125 may store mapper data in the database 130. Such data provides mappings of transmission types to transaction objects (e.g., payments, deposits, etc.). Other data stored in the transaction database 130 may include a type of transaction object, a type of transition state, a start time of the transaction state, an end time of the transaction state, duration, and the like.

In one embodiment, a computing system 135 hosts object lifecycle analysis tool 127. The analysis tool 127 generates graphs of test transaction data processed by the transaction management application 125. The graphs allow users (e.g., system administrators, developers, chief technology officers, etc.) to analyze performance issues in the application server 120 and the application 125. For example, such performance issues may include problems in concurrency (e.g., bottlenecks, pinch points, memory leaks, etc.). The graphs may display transaction objects that are created and transitions states for each of the transaction objects.

To generate an object lifecycle analysis graph, the user creates a set of test run data. The test run data is separate from actual production data and is used to provide a measure of performance of the transaction management application 125 sufficient to generate a performance graph. The test run data provides a set of transaction objects that include a distinct run tag that indicates that the set of transaction objects are test run data. Each set of test run data includes a distinct run tag to allow for fast retrieval from the transaction database. The user sends the test run data to the transaction management application 125. In turn, the transaction management application 125 receives the test run data as if the data were normal transaction data and processes the test run data. As the transaction management application 125 processes each test run object, data corresponding to each test run transaction object is stored in the transaction database 130 with the run tag. Thereafter, the analysis tool 127 may query the transaction database 130 to retrieve information about the test run data processed, such as state information, number of transactions processed per second, total transaction count, duration information, etc. The analysis tool 127 uses the retrieved information to generate a graph.

FIG. 2 illustrates an example transaction state graph 200 generated by the analysis tool 127, according to one embodiment. The transaction state graph 200 displays a logarithmic scale of test run data objects in-flight in the system. More specifically, the transaction state graph 200 displays transition states over a period time with respect to an amount of test run transition state objects in graph 205. Using a logarithmic scale allows a user of the analysis tool 127 to view objects that have a small amount of instances as well as objects with a large amount of instances. Alternatively, the analysis tool 127 may display the transaction state graph 200 using a linear scale (not shown) to allow users to view objects that contain a large amount of instances.

Legend 210 lists transition states with corresponding lines. While the transaction management application 125 processes a transaction through the application server 120, the transaction enters various transition states. As shown, the transition states include “PAY_ORIG,” “LIQUIDITY_RESPONSE,” “PAYMENT_ACK,” “PAY_ORIG_BAT,” “PAYMENT_INS,” “LIQUIDITY_REQUEST,” and “GATEWAY_ACK.” For example, when a payment transaction is initiated, the transaction may be in a “PAY_ORIG” state. Illustratively, the transaction state graph 200 depicts a scenario where the transition states are generally not being processed in a concurrent fashion. For instance, the “GATEWAY_ACK” transition states do not begin until the test run data is almost halfway processed.

The transaction state graph 200 displays data relevant to a user desiring to improve concurrency in the transactions being processed by the system. By observing the information displayed on the transaction state graph 200, the user may be able to tune the transaction management application 125 accordingly to reduce the influence of bottlenecks on throughput. For example, the user may identify problem areas in processing by observing when certain transaction states begin and end relative to other transaction states. As stated, the graph in FIG. 2 displays information that allows the user to observe that “GATEWAY_ACK” transition states do not begin until halfway through the test run. With this information, the user may identify concurrency bottlenecks and determine a cause for the bottlenecks in the underlying application or a solution for eliminating the bottlenecks.

FIG. 3 illustrates another example transaction state graph 300 generated by the analysis tool 127, according to one embodiment. Assume that the transaction state graph 300 was generated after the user tuned the transaction management application based on what was observed in the transaction state graph 200. Illustratively, as demonstrated by the distribution of the transition states over time, the transaction objects are being processed with more concurrency.

FIG. 4 illustrates an object lifecycle analysis tool 400, according to one embodiment. As stated, the analysis tool generates a graph that displays a distribution of different transition states for transaction objects over time. As shown, the analysis tool includes a database retrieval component 405 and a graphing component 410.

The database retrieval component 405 is configured to query a transaction database for transition state information for transaction objects. Doing so allows the database retrieval component 405 to obtain information relevant in generating the analytical graph, such as temporal information for each transition state (e.g., beginning and end times, durations, etc.), type names of transition states, type names for transaction objects, and the like.

In one embodiment, data obtained by the database retrieval component 405 may include test run data generated and processed into the transaction database. To create test run data to store in the transaction database, a user (e.g., a system administrator) may generate a set of transaction objects that include an identifiable run tag. The user transmits the test run data to the transaction management application. In turn, the transaction management application processes the test run data as regular transaction data. As each transaction in the test run data is processed, the transaction management application 125 stores transition state information in the transaction database 130. The transition state information stored in the transaction database 130 includes the run tag used to distinguish the processed test run data from transaction data processed normally.

For example, the transition state information may include a beginning and ending times of each transition state, a duration of each state, a transaction count, transactions per second, and the like. Further, any transition state information related to the test data includes the run tag. Thus, when the database component 405 executes a query to retrieve data from the transaction database, the database component 405 obtains all transition state information relating to the test data associated with a given run tag.

The graphing component 410 generates the analytic graph. Once receiving the information from the database, the graphing component 410 organizes transition states associated with each transaction object into a chronological order.

In one embodiment, the graphing component 410 creates timeline database tables corresponding to the transaction states. The graphing component 410 reorganizes data obtained from the transaction database 130 chronologically and stores the organized data in the timeline tables. The graphing component 410 accumulates active transition states that had been processed in a given second with a given duration time (by subtype and status). The graphing component 410 stores the results in the timeline table corresponding to the object. After storing the results in the timeline tables, the graphing component 410 uses the timeline tables to create a graph for each table. The graphing component 410 generates the graphs. The graphing component 410 may output the graph to a spreadsheet that a user may later analyze. The spreadsheet may also contain state transition data derived from the transaction database. The visualized data allows a user to more quickly identify bottlenecks and other performance issues by displaying different transition states for each transaction processed for a given duration.

FIG. 5 illustrates a method 500 for generating an analytic graph using the analysis tool, according to one embodiment.

As shown, the method 500 begins at step 505, where the analysis tool retrieves mapping data and state data from the transaction history database. As stated, the mapping data and the state data allow the analysis tool to associate activity with a corresponding transaction. More specifically, the mapping data provides mappings of transaction types to transaction objects processed by the financial management application. The state data provides information about transition state types. Further, the mapping data and the state data allow valid transmission types and object states to be represented in the graph.

At step 510, the analysis tool retrieves test run data from the transaction history database. For example, the analysis tool may retrieve transaction objects from the database identified using a given run tag. For each transaction, the analysis tool retrieves a total duration of the transaction, a subtype of the transaction, and state information of the transaction. Further, the analysis tool obtains a beginning time and an ending time for each state in the transaction. In addition, the analysis tool retrieves a total transaction count, a number of transactions per second metric, and a total duration of the test run process from the database. Once the test run data is gathered, the analysis tool may initialize a transaction object creation timeline table, a transaction object timeline table, and a transaction state timeline table. The analysis tool uses the timeline tables to store results of processing respective data.

At step 515, the analysis tool populates the timeline tables with the test run data gathered from the database based on the beginning times and ending time information. To do so, the analysis tool identifies transmission objects being processed for each second of the test run process and stores the results in the object creation timeline table. Further, the analysis tool identifies the transaction objects being processed for each second of the test run process and stores the results in the transaction object timeline table. The analysis tool processes the transaction states being processed for each second of the test run process and stores the results in the transaction state timeline table. The analysis tool processes the transaction states.

At step 520, after populating the timeline tables, the analysis tool generates a graph of the results stored in the timeline tables. The resulting graph displays a visualization of each transaction state for all transaction objects over the duration of the test run.

FIG. 6 illustrates an example computing system 600, according to one embodiment. As shown, computing system 600 includes, without limitation, a multithreaded central processing unit (CPU) 605, a network interface 615, a memory 620, and storage 630, each connected to a bus 617. Computing system 600 may also include an I/O device interface 610 connecting I/O devices 612 (e.g., keyboard, display and mouse devices) to the computing system 600. Further, in context of this disclosure, the computing elements shown in computing system 600 may correspond to a physical computing system (e.g., a system in a data center) or may be a virtual computing instance executing within a computing cloud.

CPU 605 retrieves and executes programming instructions stored in memory 620 as well as stores and retrieves application data residing in the storage 630. The interconnect 617 is used to transmit programming instructions and application data between CPU 605, I/O devices interface 610, storage 630, network interface 615, and memory 620. Note, CPU 605 is included to be representative of a single CPU, multiple CPUs, a single CPU having multiple processing cores, and the like. Memory 620 is generally included to be representative of a random access memory. Storage 630 may be a disk drive storage device. Although shown as a single unit, storage 630 may be a combination of fixed and/or removable storage devices, such as fixed disc drives, removable memory cards, or optical storage, network attached storage (NAS), or a storage area-network (SAN).

Illustratively, memory 620 includes an analysis tool 625. Storage 630 includes transaction data, a transaction table 634, and graph data 636. The analysis tool 625 processes the transaction data 632 obtained from a transaction database to generate an analytic graph to use in performance analysis. The analysis tool itself includes a database retrieval component 627 and a graphing component 629.

The database retrieval component 627 communicates with a transaction database to obtain information relevant to generating the analytic graph, such as transaction object types, subtypes, states, durations, etc. The graphing component 629 organizes the data chronologically into the state transition table 634. The graphing component 629 processes the state transition table 634 to generate the graph data 646 receives search queries and generates a culinary recipe based on the search query using text analytics.

The descriptions of the various embodiments of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terminology used herein was chosen to best explain the principles of the embodiments, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

Embodiments of the invention may be provided to end users through a cloud computing infrastructure. Cloud computing generally refers to the provision of scalable computing resources as a service over a network. More formally, cloud computing may be defined as a computing capability that provides an abstraction between the computing resource and its underlying technical architecture (e.g., servers, storage, networks), enabling convenient, on-demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction. Thus, cloud computing allows a user to access virtual computing resources (e.g., storage, data, applications, and even complete virtualized computing systems) in “the cloud,” without regard for the underlying physical systems (or locations of those systems) used to provide the computing resources.

Typically, cloud computing resources are provided to a user on a pay-per-use basis, where users are charged only for the computing resources actually used (e.g. an amount of storage space consumed by a user or a number of virtualized systems instantiated by the user). A user can access any of the resources that reside in the cloud at any time, and from anywhere across the Internet. In context of the present invention, a user may access applications or related data available in the cloud. For example, the analysis tool could execute on a computing system in the cloud and generate analytical graphs based on transaction data obtained from a transaction database. In such a case, the analysis tool could store the generated graphs (e.g., in a spreadsheet format) and collected transition state information at a storage location in the cloud. Doing so allows a user to access this information from any computing system attached to a network connected to the cloud (e.g., the Internet).

The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

While the foregoing is directed to embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow. 

What is claimed is:
 1. A computer program product for identifying concurrency bottlenecks occurring while processing lifecycle transactions from an initiation state to a completion state by visualizing said lifecycles transactions when processed concurrently, the computer program product comprising: a non-transitory computer-readable storage medium having computer-readable program code embodied therewith, wherein the code, when executed by a processor, performs an operation, the operation comprising: generating, for each of the lifecycle transactions, a plurality of transaction objects that include an identifiable run tag that distinguishes a set of test run data from other transaction data being normally processed; receiving, the set of test run data comprising the plurality of transaction objects, each of the transaction objects having a specified identifier indicating that each of the transaction objects is associated with the set of test run data and each of the respective transaction objects defined by a set of operations that together perform a task relating to each of the lifecycle transactions; sending, the set of test run data to an application; processing by the application the set of test run data; storing by the application in timeline tables of a transaction database, transition state information for each of the respective transaction objects, processed in each second for a duration of time by subtype and status of each of the lifecycle transactions corresponding to each of the transaction objects having been processed, wherein the transition state information corresponding to each of the transaction objects results from the application performing one or more of the operations in the set of operations associated with each of the transaction objects; generating, a database query that uses, at least in part, the specified identifier to retrieve the transition state information corresponding to all of the transaction objects associated with the set of test run data; executing, the database query against the transaction database to retrieve the transition state information corresponding to all of the transaction objects associated with the set of test run data from the transaction database; as each of the lifecycle transactions in the set of test run data is processed, storing, the transition state information in the transaction database including beginning and ending times of each transition state, a duration of each transition state, a transaction count, and transactions per second; organizing, the transition state associated with each of the transaction objects into a chronological order; reorganizing, the transition state information obtained from the transaction database chronologically and storing the reorganized transition state in the timeline tables; accumulating, active transition states that had been processed in each second for the duration of time by the subtype and the status of each of the lifecycle transactions; storing, results of the accumulated active transition states in a timeline table of the timeline tables corresponding to each transaction object; mappings, transaction types to the transaction objects as representations of a graph; retrieving, the mappings and transition state information from a history of each of the lifecycle transactions; retrieving, a total duration of each lifecycle transaction, a subtype of each lifecycle transaction, and the transition state information of each lifecycle transaction; obtaining, the beginning time and the ending time for each transition state in each lifecycle transaction; retrieving, from the transaction database, a total transaction count, a number of transactions per second, and a total duration of the set of test run data; initializing, after gathering the set of test run data, a transaction object creation timeline table, a transaction object timeline table, and a transaction state timeline table of the timeline tables; populating, the timeline tables with the set of test run data gathered from the transaction database based on the beginning time and the ending time to identify the transaction objects being processed for each second of the test run data and storing results of the processed transaction objects in the object creation timeline table; identifying, the transaction objects being processed for each second of the test run data and storing the results in the transaction object timeline table; processing, the transaction states being processed for each second of the test run data and storing results of the processed transaction states in the transaction state timeline table; generating, after processing the transaction states, the graph of the transition state information for each transaction object in a logarithmic scale based on the reorganized transition state information and the timeline tables; and outputting, the graph into a spreadsheet to identify the concurrency bottlenecks occurring while processing the lifecycle transactions from the initiation state to the completion state.
 2. The computer program product of claim 1, wherein each transaction object corresponds to another instance of a transaction of the lifecycle transactions.
 3. The computer program product of claim 1, wherein the duration of time is equal to one second.
 4. A system comprising: a processor; and a memory storing a program which, when executed on the processor, performs an operation for identifying concurrency bottlenecks occurring while processing lifecycle transactions from an initiation state to a completion state by visualizing said lifecycles transactions when processed concurrently, the operation comprising: generating, for each of the lifecycle transactions, a plurality of transaction objects that include an identifiable run tag that distinguishes a set of test run data from other transaction data being normally processed; receiving, the set of test run data comprising the plurality of transaction objects, each of the transaction objects having a specified identifier indicating that each of the transaction objects is associated with the set of test run data and each of the respective transaction objects defined by a set of operations that together perform a task relating to each of the lifecycle transactions; sending, the set of test run data to an application; processing by the application the set of test run data; storing by the application in timeline tables of a transaction database, transition state information for each of the respective transaction objects, processed in each second for a duration of time by subtype and status of each of the lifecycle transactions corresponding to each of the transaction objects having been processed, wherein the transition state information corresponding to each of the transaction objects results from the application performing one or more of the operations in the set of operations associated with each of the transaction objects; generating, a database query that uses, at least in part, the specified identifier to retrieve the transition state information corresponding to all of the transaction objects associated with the set of test run data; executing, the database query against the transaction database to retrieve the transition state information corresponding to all of the transaction objects associated with the set of test run data from the transaction database; as each of the lifecycle transactions in the set of test run data is processed, storing, the transition state information in the transaction database including beginning and ending times of each transition state, a duration of each transition state, a transaction count, and transactions per second; organizing, the transition state associated with each of the transaction objects into a chronological order; reorganizing, the transition state information obtained from the transaction database chronologically and storing the reorganized transition state in the timeline tables; accumulating, active transition states that had been processed in each second for the duration of time by the subtype and the status of each of the lifecycle transactions; storing, results of the accumulated active transition states in a timeline table of the timeline tables corresponding to each transaction object; mappings, transaction types to the transaction objects as representations of a graph; retrieving, the mappings and transition state information from a history of each of the lifecycle transactions; retrieving, a total duration of each lifecycle transaction, a subtype of each lifecycle transaction, and the transition state information of each lifecycle transaction; obtaining, the beginning time and the ending time for each transition state in each lifecycle transaction; retrieving, from the transaction database, a total transaction count, a number of transactions per second, and a total duration of the set of test run data; initializing, after gathering the set of test run data, a transaction object creation timeline table, a transaction object timeline table, and a transaction state timeline table of the timeline tables; populating, the timeline tables with the set of test run data gathered from the transaction database based on the beginning time and the ending time to identify the transaction objects being processed for each second of the test run data and storing results of the processed transaction objects in the object creation timeline table; identifying, the transaction objects being processed for each second of the test run data and storing the results in the transaction object timeline table; processing, the transaction states being processed for each second of the test run data and storing results of the processed transaction states in the transaction state timeline table; generating, after processing the transaction states, the graph of the transition state information for each transaction object in a logarithmic scale based on the reorganized transition state information and the timeline tables; and outputting, the graph into a spreadsheet to identify the concurrency bottlenecks occurring while processing the lifecycle transactions from the initiation state to the completion state.
 5. The system of claim 4, wherein each transaction object corresponds to another instance of a transaction of the lifecycle transactions.
 6. The system of claim 4, wherein the duration of time is equal to one second. 